-
-
Notifications
You must be signed in to change notification settings - Fork 489
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
MBean registration / Ignore existing #5670
Conversation
Looks to also happen on Links API even with one webapp
Not sure why ? |
When running multiple GeoNetwork on same Jetty, the following error will happen on startup ``` 2021-05-04 14:30:51,431 ERROR [jeeves] - JeevesContextLoaderListener: Error creating bean with name 'org.fao.geonet.camelPeriodicProducer.MessageProducerFactory#0': Invocation of init method failed; nested exception is org.quartz.SchedulerException: Unable to register scheduler with MBeanServer. [See nested exception: javax.management.InstanceAlreadyExistsException: quartz:type=QuartzScheduler,name=DefaultQuartzScheduler-harvest-wfs,instance=NON_CLUSTERED] ``` and one of the web app will not be available. Using IGNORE_EXISTING registration policy seems to solve the issue but is maybe not the perfect fix ?
b70b523
to
c499106
Compare
…n't make it work. In debug mode evaluating servletContext.getContextPath works fine even on the MockServletContext, so not sure why the exception is triggered.
…irectly, let spring autowire beans properly.
It happened to me running just one GeoNetwork 4 instance using core-geonetwork/services/src/main/java/org/fao/geonet/api/links/LinksApi.java Lines 111 to 122 in da4fe67
javax.management.InstanceAlreadyExistsException: geonetwork:name=url-check,idx=empty-slot-0 is thrown.
|
Added with #6188 |
When running multiple GeoNetwork on same Jetty, the following error will happen on startup
and one of the web app will not be available.
Using IGNORE_EXISTING registration policy seems to solve the issue but is maybe not the perfect fix ?
It looks like progress status are mixed up between apps. So maybe some progress indicator ids should contain webapp name or node uuid ?
@cmangeat any experience on this ?